fix: Adding a hardcoded createdBy parameter to the deploy.yml file to prevent validation pipeline failures caused by the deployer function in the Bicep file.#448
Merged
Conversation
…ent validation pipeline failures caused by the deployer function in the Bicep file.
NirajC-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
Roopan-Microsoft
approved these changes
Sep 5, 2025
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
deepammi
pushed a commit
to deepammi/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator
that referenced
this pull request
Dec 7, 2025
…inyml fix: Adding a hardcoded createdBy parameter to the deploy.yml file to prevent validation pipeline failures caused by the deployer function in the Bicep file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces a small but important improvement to how resource tags are set during deployment. The main change is to make the "CreatedBy" tag more flexible and allow it to be set via a parameter, rather than always deriving it from the deployer’s principal name.
Tagging improvements:
createdByparameter toinfra/main.bicep, allowing the "CreatedBy" tag to be explicitly set or default to the deployer's username if not provided..github/workflows/deploy.ymlto pass acreatedBy="Pipeline"value when running deployments, ensuring resources created by the pipeline are tagged accordingly.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information